twd: generator friendly

September 14 2025

As I continue to dread updating this website more and more because of the crippling tech debt I can feel looming around the corner, I finally decided to tidy up a bit by reorganizing the website structure! As we approach the Bill Wurtz website the key thing I need to do is move my blogposts off of a single page and onto multiple others. Here is a diagram of the current server layout right now:
As you can see this is kind of rough, even though we don't have many blog posts to worry about yet the hefty category is already kind of slowing down, and it makes asset management a complete mess as we scale up to add potentially different categories and blog posts.

So how do we fix this? I present to you my magnum opus, a new name-based organization system!
Is this a good idea? Probably, I can't think of any reason this could turn problematic as it scales up but system architecture is an art. I chose to do name based because I plan on having equinox automatically sort and organize assets, and if I'm already providing the title and it can grab the date, then it should be able to easily index through both assets and blog folders under the rules outlined in the diagram.

I envision equinox reading from the webserver directory to see what folders are present, dynamically informing it which blog categories are available and then representing them as a dropdown. Upon clicking generate it'll grab the necessary headers from the "hub" page (that way we can update all relative navbar links automatically) and then also place the page into its respective folder, update the hub page listing, and use the same navigation to populate the assets folder, making auto generating references to assets super clean as well (if pages are in topic/entry, then assets are also in assets/topic/entry). Tune in next time when I actually get it to do this, and then we can start to tackle the huge part of this project being a proper rich text editor compliant with markdown spec.